Tech Arsenal 1

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 1 / Tech Arsenal (Arsenal Computer).ISO / tek-05 / lwp41.txt < prev next >

Wrap

Text File | 1993-03-09 | 33.9 KB | 644 lines

This text file summarizes the features of LAN WorkPlace for DOS v4.1 and the new LAN WorkGroup product with a reasonable degree of technical detail. A quick summary of what's new in v4.1 is included at the end of the document. I.) Background Information In April of 1991, Novell released LAN WorkPlace for DOS v4.0, a media- independent TCP/IP services product for DOS and Windows users. Since then, the LAN WorkPlace family of products has become very popular with over 300,000 nodes sold. LAN WorkPlace for DOS v4.01 has been recognized as a top-notch TCP/IP platform and has won PC Magazine's Editor's Choice award in a review of 5 competing TCP/IP packages suitable for use with NetWare. In October of 1992, Novell announced an important new release of LAN WorkPlace for DOS -- version 4.1. This release adds the ability to use serial lines for TCP/IP networking via SLIP (Serial Line Internet Protocol) or PPP (Point to Point Protocol), as well as SNMP management capabilities and large array of other new features. At the same time, a new product targeted at larger NetWare v3.11 installations requiring TCP/IP integration was announced called "LAN WorkGroup". LAN WorkGroup builds upon the LAN WorkPlace product by adding centralized, server-based installation along with a BOOTP server NLM that provides individual nodes with all of the requisite IP addressing information, thereby alleviating the need for an administrator to visit each workstation and perform the installation of the TCP/IP networking software. International users of LAN WorkPlace or LAN WorkGroup will be pleased to know that the products are fully enabled for localization to their native language (even for alphabets requiring double-byte character sets). In fact, efforts are now underway to bring out LAN WorkPlace in French, German, Spanish, Portuguese, Italian and Japanese. Central to the product is the Novell TCP/IP Transport for DOS/Windows, a TCP/IP protocol stack built by Novell to provide users with high- performance TCP/IP support in a variety of DOS environments while occupying a minimum amount of system memory. While this TCP/IP implementation uses ODI (Open Data-link Interface) drivers to coexist peacefully with NetWare protocols on a single network interface card, the presence of NetWare is not a requirement for running LAN WorkPlace for DOS. Indeed, many customers use LAN WorkPlace all by itself, or in conjunction with other network operating systems such as Microsoft LAN Manager, IBM LAN Server or Banyan VINES. The TCP/IP in LAN WorkPlace also allows DOS and Windows-based NetWare clients to connect directly to NetWare v3.11 servers that are accessible only via TCP/IP routes, or to coexist with NetWare servers in an environment where only TCP/IP transport protocols are to be used on the network. This NetWare client over IP capability involves a mechanism that encapsulates IPX packets withing UDP/IP packets called "IP Tunneling" which is defined in RFC-1234. The TCP/IP transport facilities are augmented by two complete sets of applications (one for Windows, one for DOS) that provide common TCP/IP services such as file transfer and terminal emulation capabilities for both Windows and conventional DOS environments. While the most common applications used in TCP/IP networking are included with the package, the TCP/IP Transport in LAN WorkPlace for DOS provides an open set of APIs that enable a variety of networking applications from 3rd-party software vendors. 3rd-party software options include support for X-Windows applications, distributed database management systems and sophisticated image processing systems. Two of these "3rd-party" networking options for LAN WorkPlace are available from Novell. These are the OpenConnect TN3270 for DOS -- now sold and supported by Novell as "TN3270 for LAN WorkPlace", and Beame & Whiteside's "BW-NFS/LAN WorkPlace" now available in a red box labeled "NFS Client for LAN WorkPlace". Developers wishing to write their own DOS and Windows applications that use TCP/IP will want the programmer's version of LAN WorkPlace (LAN WorkPlace for DOS Toolkit), or the LAN WorkShop Software Developer's Kit, which combines the LAN WorkPlace Toolkit for DOS with the corresponding toolkits for OS/2 and the Macintosh along with TI-RPC (Transport Independent Remote Procedure Call) libraries for DOS, Windows and OS/2 applications. For more information about obtaining these software developer kits, contact Novell's Professional Developer's Program by phoning 800-RED-Word from the United States, or 512-794-1796 from elsewhere. II.) LAN WorkPlace for DOS Product Overview -- The Novell TCP/IP Transport for DOS/Windows -- The Novell TCP/IP Transport for DOS/Windows is an implementation of TCP/IP that supports up to 64 TCP and 32 UDP connections simultaneously on behalf of multiple DOS and/or Windows-based applications. It can be utilized on a variety of media, including Ethernet, Token-Ring, Arcnet, FDDI, Packet Radio and Asynchronous serial connections. Indeed, any kind of interface with a corresponding ODI driver can be used. Supported standards include: IP (Internet Protocol) - RFC 791 IP Subnet Extension - RFC 950 IP Broadcast Datagrams - RFC 922 IP Broadcast Datagrams with Subnets - RFC 922 IP on Ethernet - RFC 894 IP on ARCnet - RFC 1201 IP on IEEE 802.2 - RFC 1042 IP on SLIP (Serial Line Internet Protocol) - RFCs 1055, 1144 IP on (async) PPP (Point to Point Protocol) - RFCs 1331, 1332, 1333, 1334 TCP (Transmission Control Protocol) - RFC 793 UDP (User Datagram Protocol) - RFC 768 ICMP (Internet Control Message Protocol) - RFC 903 ARP (Address Resolution Protocol) - RFC 826 RARP (Reverse Address Resolution Protocol) - RFC 903 BOOTP (Bootstrap Protocol) - RFCs 951, 1084 DNS (Domain Name System) - RFCs 1034, 1035, 1183 SNMP (Simple Network Management Protocol) - RFCs 1156, 1157, 1213 NetBIOS over TCP/IP - RFCs 1001, 1002 TCP/IP Transport features: * BOOTP client configuration. By broadcasting "BOOTP Request" packet, and receiving a reply from any standard BOOTP server, the Novell TCP/IP Transport (TCPIP.EXE) can obtain the following IP configuration info from a BOOTP server: - IP Address - Subnet Mask - Domain Name - Domain Name Server address(es) - Default Router IP Address * A BOOTP check utility. This utility sends a BOOTP request packet then reports the IP address(es) of any active BOOTP servers and whether or not any conflicting information for the local node is received from more than one BOOTP server. * RARP. The TCP/IP kernel can obtain its IP address using RARP. In this case, other IP addressing information such as subnet mask and DNS particulars must be contained in an ASCII configuration file (NET.CFG). * A RARP server TSR. This TSR (RARPD.EXE) can be loaded in DOS memory and provides IP addresses to RARP requests. It runs in the background on any DOS or Windows machine while consuming 800 bytes of RAM, plus an additional 10 bytes for each MAC to IP address mapping. * SNMP. An SNMP agent (SNMP.EXE) is included. This SNMP agent is a DOS TSR (Terminate and Stay Resident) program that can be loaded into memory if desired. When loaded, it can supply remote SNMP monitoring applications with relevant MIB 1 and MIB II statistics about the workstation's TCP/IP transport stack. SNMP.EXE consumes 22KB when resident, can be unloaded with a command line option, and gets its "monitor" and "control" community name variables from NET.CFG. This SNMP agent does not provide an API that enables software developers to register custom objects with the agent. However, Novell is chartered with developing the SNMP agent for the DMTF (Desktop Management Task Force) which will provide such an API. * LAN WorkPlace Console. This menu driven DOS application (LWPCON.EXE) provides all of the SNMP monitoring capabilities of NetWare v3.11's "TCPCON", among other things. It provides for the management of the local PC's TCP/IP transport (with or without SNMP.EXE loaded) and for the management of other LAN WorkPlace nodes that are running SNMP.EXE. The application also provides for various other IP network related functions. Utilities include: - Domain Name System lookup - Echo Test - IP Trace Route - ODI Interface statistics - SNMP manager (for MIB I and II objects) - A mechanism that checks for active TCP services on remote hosts. * SLIP (Serial Line Internet Protocol) and PPP (Point to Point Protocol) support. SLIP and PPP support is provided in the form of a custom ODI driver for LAN WorkPlace: SLIP_PPP.COM. This driver allows the Novell TCP/IP Transport for DOS v4.1 to use asynchronous connections for IP services required by DOS and Windows applications. It supports the following: - SLIP - Compressed SLIP (C-SLIP) using Van Jacobson TCP/IP header compression (as described in RFC-1144). - PPP with support for Van Jacobson TCP/IP header compression option negotiation and PAP (Password Authentication Protocol) as described in RFC-1334. - Support for National Semiconductor's 16550, 16550A, 16450 and 8250 UARTs (Universal Asynchronous Receiver Transmitter). Use of a 16550 UART is strongly recommended (and is required for use with Windows at speeds of 9600bps or greater). NOTE: One can use the Microsoft Diagnostics program supplied with Windows v3.1 (MSD.EXE) to determine which type of UART is installed in a PC. - Interface speeds up to 57,600 bps when used with a V.32bis/V.42bis modem and 16550A UART. * Support for multiple IP addresses. This feature allows for connections to two IP networks simultaneously (for example, an Ethernet connection and a PPP connection via an async line). This support does NOT include IP routing capabilities. * PING -- a common tool for TCP/IP network nodes, PING.EXE implements an ICMP (Internet Control Message Protocol) echo test for determining whether or not a particular IP node or workstation is reachable. * "IP Tunneling" is implemented as an ODI LAN driver, or "MLID" (Multiple Link Interface Driver) called "IPTUNNEL.EXE" that encapsulates IPX datagrams in UDP/IP packets according to RFC 1234. This allows a DOS/Windows-based NetWare client to attach to NetWare servers on a remote IPX network segment that is accessible only via TCP/IP, and run any application that uses IPX/SPX transports. * NetBIOS over TCP/IP (RFCNBIOS.EXE) provides the NetBIOS session- layer API over TCP/IP conforming to RFCs 1001 and 1002. This is a standard B-node implementation of RFC-NetBIOS with the added ability to allow for mapping a NetBIOS node-name to a remote IP address, so that connections can be established across IP routers. * Built-in Windows awareness. A Windows "Virtual Machine Interface" device driver (VTCPIP.386) allows DOS applications and standard or protected-mode Windows applications to access and share the reentrant TCP/IP kernel (TCPIP.EXE) simultaneously. A Windows DLL (Dynamic Link Library) "WLIBSOCK.DLL", allows Windows applications built using the Berkeley Socket model easy access to TCP/IP services. This module supports the TCP/IP service applcations included in LAN WorkPlace, and also provides a stable API for Windows applications available from many leading software developers. -- LAN WorkPlace TCP/IP Services for Windows -- * "Host Presenter" is a Windows-based DEC VT-series terminal emulator that allows for up to ten simultaneous Telnet connections to one or more TCP/IP-equipped hosts ("Telnet" is a fairly general, bi-directional communications facility that uses TCP connections primarily for virtual terminal service and is defined in RFC-854). Host Presenter works in conjunction with a Windows based script-management application called "Script Director", allowing scripts written using an extensive script language called "ScreenPlay" to be invoked automatically by a loading session "profile" or from a predefined keystroke. Host Presenter is now much faster that the v4.0x version, and no longer requires that TelAPI.EXE to be loaded in memory prior to invoking Windows (thereby saving approximately 20KB of conventional or UMB RAM in DOS sessions). Telnet service is now provided by a Windows DLL that insulates Host Presenter from the underlying transport service to be used. Transport service DLLs provided in v4.1 include support for Telnet (TELNET.DLL) and Asynchronous (ASYNC.DLL) communications. The latter allows Host Presenter to be used with standard modems. The TELNET.DLL supports up to ten simultaneous sessions. This new architecture for Host Presenter allows us to create new transport DLLs in the future without requiring further modification of Host Presenter (for example, a NetWare Virtual Terminal DLL for IPX-based communication to UNIX hosts running an implementation of NetWare for UNIX). Also new in the v4.1 release: - ISO Latin-1 (8859) character set in Host Presenter Font (this adds to the pre-existing DEC multinational character set of the Host Presenter font). - Improved Printer support that translates DEC VT-series character attributes into Windows print attributes and allows for on-the-fly configuration of the Windows default printer. - Adjustable scroll rates (a user-specified number of lines to be scrolled prior to screen updates) in lieu of the standard DEC VT-series "jump-scroll" option. - The ability to select an alternate TCP port destinations on a session-by-session basis. * Rapid Filer (formerly "File Express") is a Windows-based FTP (File Transfer Protocol - see RFCs 949 and 959) client that vastly simplifies use of the FTP standard by using a graphical user interface that allows for "drag and drop" file copies between local and remote file systems via FTP. Rapid Filer now supports additional remote file system types, including: DOS, MVS, NetWare OS/2, UNIX, VM, VMS and "other". Features include: - The ability to print files located on remote file systems through any Windows-defined printer with the click of the mouse. - Automatic file type recognition which obviates the need for the user to specify whether a file to be transferred is ASCII, Binary or VMS Record structure. - Recursive directory tree copies. - Recursive directory tree deletion - Various options for handling file overwrites and file name incompatibilities between different operating systems. In these cases, the user can instruct Rapid Filer to: A.) Automatically rename the new version of a file. B.) Skip the file copy operation and proceed C.) Overwrite the existing version of a file D.) Prompt the user for instructions to do one of the above, or to input a new filename. - A new "Protocol Window" which displays the FTP dialogue between the PC and remote host, and also allows the user to manually issue site-specific FTP protocol commands normally done using the FTP "quote" command in command-line oriented FTP implementations. - OLE support that enables the user to drag files or subdirectories from the Windows v3.1 File Manager (or the Norton Desktop for Windows) to a remote file system window to initiate an FTP "put" or "mput" operation. * Serving FTP. This Windows-based FTP server runs in the background, allowing remote users to retrieve and store files on the PC's local or network attached disk drives. Features include: - Multiple Session support. - Improved security over the prior version. An encrypted, password-protected password file can be created that allows for the definition of "full-access" and "guest" users. Guest users have no password, and are restricted to read- only access within a specific directory tree. - Enhanced activity logging facilities. * Windows Talk. This is an implementation of the UNIX talk program for Windows users. "Talk" allows two users to initiate a visual chat session where their keystrokes are displayed on each of their terminals simultaneously. The Talk program can be used to initiate sessions, and will also listen for remote users trying to establish a Talk session with the Windows user. * Finger and Fingerd. These Windows applications implement finger, a mechanism for displaying information about users on networked hosts. The finger daemon reports the contents of an ASCII file called "PLAN.TXT". * Windows RSH. This Windows application implements the rsh (remote shell) command. Results of remote commands can be easily copied into other Windows applications via the Windows Clipboard. * IP Resolver. This DNS/hosts file look-up utility allows users to query a DNS server and/or a hosts file to translate host names to IP addresses and vice-versa. It also allows users to send an ICMP echo message ("ping") to a remote host to verify connectivity to it. * Extensive and comprehensive online help for all LAN WorkPlace Windows-based applications is provided through a "Master" help file index. -- LAN WorkPlace TCP/IP Services for DOS -- All conventional DOS applications included with LAN WorkPlace are designed to operate correctly and simultaneously when run under multitasking DOS environments such as Microsoft Windows or DESQview. * FTP and FTPd -- FTP provides a traditional command-line interface common to the File Transfer Protocol. Unique features of Novell's FTP client include the ability to automatically determine file structures (whether the file is ASCII, binary or VMS record format), the ability to do recursive directory copies, and the ability to transfer files between two remote hosts regardless of whether or not those remote hosts support the Sun FTP proxy extensions. FTPd allows a DOS machine to act as an FTP server without requiring Windows and Serving FTP. * TNVT220 is a character-based DEC VT-series terminal emulator that supports up to ten simultaneous telnet sessions to one or more host(s). The v4.1 version of TNVT220.EXE no longer requires TelAPI.EXE to be pre-loaded in memory prior to invoking it (thereby saving roughly 20KB of conventional or UBM RAM). * TelAPI (Telnet Application Programming Interface). TelAPI is a RAM-resident telnet engine that allows 3rd-party communications programs and terminal emulators to utilize Telnet connections to host systems. Any program that supports a standard LAN communication interface can use TelAPI. Supported LAN communication interfaces now include: NASI (NetWare Asynchronous Services Interface), Int14, BAPI (Bridge-3Com API), UB-NetCI (Ungermann-Bass Net Command Interpreter), EtherTERM and the TelAPI Extended Int14 interface. These interfaces are documented thoroughly in the Telnet API Reference Manual (a component of the "LAN WorkPlace for DOS Toolkit" package). A companion utility called "TSU" (Telnet Session Utility) is provided to assist in establishing Telnet connections to host systems on behalf of applications that don't support the TelAPI Extended Int14 mechanisms directly (for example, an emulator supporting only Int14 connections). TelAPI's support of standard Int14 connections is now significantly faster than in previous versions. * R-Utilities -- rsh (remote shell) and rexec (remote execute) enable a user to invoke commands on a UNIX system remotely. rcp (remote copy) copies files and directory trees between NetWare, DOS and UNIX file systems and supports automatic recognition of ASCII or binary file types (ASCII files are automatically converted to the format of the target file system when used in this mode). rpr, rps and rpd (remote print) allow the user to submit files to, and manipulate remote host print queues via the remote host's rsh daemon. * XPC. This new ram-resident program allows for the remote control of a DOS machine via a Telnet or X-Windows connection for running character-based DOS applications. This remote control utility (XPC.EXE) consumes 61KB of RAM (or 14KB of conventional RAM if an EMS memory manager is active). Using XPC, a user sitting at a UNIX workstation or other TCP/IP-savvy host can remotely access character-based DOS and NetWare applications such as SYSCON via a telnet or X-Windows session. * Line Printer Daemon Protocol support. Three new utilities for printing files remotely have been added: lpr.exe, lpq.exe and lprm.exe. These commands behave much like their UNIX counterparts from the DOS prompt (see RFC 1179). * Finger. A DOS-based finger client is provided. * TFTP and TFTPd -- Client and server implementations of the Trivial File Transfer Protocol (see RFC 783). III.) RAM memory usage of DOS ODI, TCP/IP and related drivers. Drivers are listed in the approximate order in which they are loaded. Driver/TSR Description Default Size Size Range Program name (Approximate size in KB.) ------------ ------------------------- ------------ --------------- ???NET?.COM NetWare Shell 7 - 43 7 with XMS/EMS IPTUNNEL.EXE Software MLID IPXonIP 2.5 n/a IPXODI.COM NetWare SPX/IPX stack 14 9 - 14 LSL.COM Link Support Layer 20 *4.4 - 64 NE2000.COM Board-specific ODI driver 4.5 Varies with NIC SNMP.EXE SNMP Agent (optional) 22 n/a TCPIP.EXE TCP/IP protocol stack 22.5 **15 - 29 TELAPI.EXE Telnet API (if needed) 21 17 - 33 XPC.EXE LAN WorkPlace XPC 61 14 with EMS * TCPIP.EXE requires that LSL.COM be configured with at least one receive buffer equal to the maximum data segment size of your network media (1500 bytes for Ethernet), and a mempool of equal size. Therefore, a minimum resident LSL size on an Ethernet node would be about 7.4K, containing one 1500 byte receive buffer and a 1500 byte mempool. Adding more receive buffers of the same size and a larger mempool will improve performance up to a point, although the minimum is probably adequate for casual Telnet usage. The LAN WorkPlace for DOS installation procedure configures the LSL to contain 8 buffers of 1500 bytes and a 4K mempool, yielding an LSL RAM size of roughly 20KB (this may be considered excessive for all but the most demanding users who require a substantial number of active network connections). ** It is possible to adjust the resident size of the TCP/IP stack by configuring it for fewer usable TCP connections. With 4 TCP connections (allowing for 2 Telnet sessions and one FTP session at the same time), and two UDP sockets available, the TCPIP.EXE resident RAM size is 19K. If only UDP/IP is being used (for those using only an NFS client, the IPTUNNEL driver for NetWare, or SNMP- based applications) then a value of zero TCP sockets can be specified. In this case none of the TCP code loads into memory, yielding a resident UDP/IP stack of about 14K. Most ODI LAN drivers, all Novell protocol stacks, and NetWare drivers operate correctly when loaded in high memory regions using 386 memory managers such as QEMM-386. All can be sequentially unloaded from RAM without having to reboot. IV.) LAN WorkPlace Toolkit for DOS LAN WorkPlace Toolkit for DOS is a super-set of the LAN WorkPlace for DOS end-user package. It is available to developers who wish to write applications for DOS and Microsoft Windows that use TCP/IP and work reliably in a NetWare environment. Any application built for LAN WorkPlace for DOS will run when using LAN WorkGroup. The following programmatic inferfaces are supported: * BSD-style Socket Library. Conforms to the Berkeley socket interface model and is current with the 4.3 Berkeley Software Distribution. Socket Libraries are included for both conventional DOS programming and for Windows the WLIBSOCK.DLL included with LAN WorkPlace and LAN WorkGroup. Support for Borland and Microsoft C compilers is provided. * TelAPI (Telnet API) The toolkit includes programmer's documentation for the TelAPI component of the end-user and developer packages. * NetBIOS (NetBIOS Service Protocol on TCP/IP) - RFCs 1001, 1002. The toolkit includes programmer's documentation for the NetBIOS component of the end-user and developer packages. Note: An OEM license is available for the TCP/IP Transport and ODI Driver components of LAN WorkPlace for DOS. This program enables software developers to include Novell's TCP/IP Transport with their applications without per/node royalties. The program involves paying Novell an annual fee, which includes ongoing updates and technical support to the developer's engineering staff. Contact Mark Troyer of Novell's Connectivity Products Group in San Jose, California for more details. Mark can be reached by phone by calling (408) 321-1117, by FAX: (408) 473-8990 or via Internet mail: mptroyer@novell.com. V.) LAN WorkShop LAN WorkShop is a Software Developer's Kit (SDK) that bundles the following developer's tools into a single, low-cost package: LAN WorkPlace for DOS Toolkit LAN WorkPlace for OS/2 Toolkit LAN WorkPlace for Macintosh Toolkit Also included are Transport Independent Remote Procedure Call (TI-RPC) libraries for DOS and Windows. Applications written using the TI-RPC libraries can be utilized over either TCP/IP or IPX/SPX. DOS and Windows Applications developed using the LAN WorkPlace for DOS Toolkit that do not utilize Asynchronous Notification Routines can be run without modification on an OS/2 v2.0 running LAN WorkPlace for OS/2. VI.) Pricing and Availability LAN WorkPlace for DOS is currently available from all Novell authorized resellers. It is offered in single, ten and one hundred user packages: Product User count Part Number Price in US$ ------------- ---------- ----------- ------------ LAN WorkPlace for DOS v4.1 -- 1 User 883-001132-002 $399 10 User 883-001300-002 $1,995 100 User 883-001754-002 $12,995 LAN WorkGroup -- (DOS/Windows) 5 User 883-002613-001 $1,500 10 User 883-002614-001 $2,495 20 User 883-002615-001 $3,495 50 User 883-002623-001 $4,995 100 User 883-002616-001 $6,995 250 User 883-002617-001 $12,495 LAN WorkPlace for OS/2 v3.0 -- 1 User 883-002494-001 $399 10 User 883-002495-002 $1,995 100 User 883-002496-002 $12,995 LAN WorkPlace for Macintosh v1.30 -- 1 User 883-002612-001 $399 10 User 883-002610-002 $1,995 100 User 883-002611-002 $12,995 TN3270 for LAN WorkPlace 1 User 883-002401-001 $145 (DOS-based) 10 User 883-002402-001 $645 100 User 883-002403-001 $3,995 NFS Client for LAN WorkPlace 1 User 883-002404-001 $295 (DOS/Windows) 10 User 883-002405-001 $1,395 100 User 883-002406-001 $8,495 *LAN WorkPlace for DOS Toolkit 1 User 884-000051-001 $399 *LAN WorkShop SDK Bundle 1 User 884-000061-001 $499 *Available through the Professional Developer's Program) These packages (with the exception of the developer products) are available through any authorized Novell reseller. For pricing outside the United States and Canada, customers should contact their local Novell Authorized reseller. For information about special upgrade pricing from prior versions of LAN WorkPlace and competitive products, call 800-346-7177 or 801-429-5414. For additional informational literature, or information about other Novell UNIX integration products please call 800-772-UNIX or send a FAX to 408-473-8990, attention: Field Marketing. For information regarding the Professional Developer's Program, call 800-REDWORD, 512-794-1796 or FAX: 512-794-1770. VII.) Brief Summary: What's new in LAN WorkPlace v4.1? New TCP/IP features: * BOOTP client configuration. * BOOTPCHK - a BOOTP configuration test program. * Serial line support (SLIP, CSLIP & PPP-capable ODI driver) * RARP server TSR * Support for up to four ODI interfaces simultaneously. * SNMP Agent (applicable MIB I & MIB II objects are reported). * LAN WorkPlace Console "LWPCON" IP network diagnostic information and SNMP manager application. Utilities include: - Domain Name System lookup - Echo Test - IP Trace Route - ODI Interface statistics - SNMP manager (for MIB I and II objects) - A mechanism that checks for active TCP services on remote hosts. * Ability to search a multiple directory path for resolv.cfg and hosts files (ie: Z:\ETC;C:\NET\TCP). * Libraries include support for the Borland C compiler as well as Microsoft C (LAN WorkPlace for DOS Toolkit and LAN WorkShop only). New Windows features and applications: * Host Presenter is faster and no longer needs TelAPI to be resident prior to invoking Windows. Also new in Host Presenter: - ISO/Latin-1 character set (commonly used on European UNIX systems) - Support for Modem connections. - Enhanced printing support. * Rapid Filer (Formerly File Express) is faster, supports "drag and drop" file copies to and from any number of FTP-accessed file systems as well as from the Windows File Manager. Profiles can now be created without embedded passwords (user is prompted when connection is established). Miscellaneous new features are also in this FTP client implementation. * Serving FTP now supports multiple sessions with enhanced security and activity logging options. * IP Resolver now can initiate an ICMP echo test (ping). * Talk (client and server) * Finger (client and server) * RSH client Note: A new master Windows help file provides extensive help for all Windows-based applications. New DOS features and Applications: * XPC - A RAM-resident Telnet server and X11 client for the remote control of character-based DOS applications from any host supporting Telnet or X-Windows. * TNVT220 no longer requires TelAPI to be resident in RAM. * Finger client. * Minor enhancements and fixes as needed for all DOS applications. * INSTALL can now be run from a network drive. Install can also update and configure ODI and NetWare client software.